<?xml version="1.0" encoding="utf-8"?>
<!--
                                                                                     
 h       t     t                ::       /     /                     t             / 
 h       t     t                ::      //    //                     t            // 
 h     ttttt ttttt ppppp sssss         //    //  y   y       sssss ttttt         //  
 hhhh    t     t   p   p s            //    //   y   y       s       t          //   
 h  hh   t     t   ppppp sssss       //    //    yyyyy       sssss   t         //    
 h   h   t     t   p         s  ::   /     /         y  ..       s   t    ..   /     
 h   h   t     t   p     sssss  ::   /     /     yyyyy  ..   sssss   t    ..   /     
                                                                                     
	<https://y.st./>
	Copyright © 2017 Alex Yst <mailto:copyright@y.st>

	This program is free software: you can redistribute it and/or modify
	it under the terms of the GNU General Public License as published by
	the Free Software Foundation, either version 3 of the License, or
	(at your option) any later version.

	This program is distributed in the hope that it will be useful,
	but WITHOUT ANY WARRANTY; without even the implied warranty of
	MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
	GNU General Public License for more details.

	You should have received a copy of the GNU General Public License
	along with this program. If not, see <https://www.gnu.org./licenses/>.
-->
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
		<base href="https://y.st./en/weblog/2017/02-February/01.xhtml" />
		<title>XHTML 5.1 &lt;https://y.st./en/weblog/2017/02-February/01.xhtml&gt;</title>
		<link rel="icon" type="image/png" href="/link/CC_BY-SA_4.0/y.st./icon.png" />
		<link rel="stylesheet" type="text/css" href="/link/basic.css" />
		<link rel="stylesheet" type="text/css" href="/link/site-specific.css" />
		<script type="text/javascript" src="/script/javascript.js" />
		<meta name="viewport" content="width=device-width" />
	</head>
	<body>
		<nav>
			<p>
				<a href="/en/">Home</a> |
				<a href="/en/a/about.xhtml">About</a> |
				<a href="/en/a/contact.xhtml">Contact</a> |
				<a href="/a/canary.txt">Canary</a> |
				<a href="/en/URI_research/"><abbr title="Uniform Resource Identifier">URI</abbr> research</a> |
				<a href="/en/opinion/">Opinions</a> |
				<a href="/en/coursework/">Coursework</a> |
				<a href="/en/law/">Law</a> |
				<a href="/en/a/links.xhtml">Links</a> |
				<a href="/en/weblog/2017/02-February/01.xhtml.asc">{this page}.asc</a>
			</p>
			<hr/>
			<p>
				Weblog index:
				<a href="/en/weblog/"><abbr title="American Standard Code for Information Interchange">ASCII</abbr> calendars</a> |
				<a href="/en/weblog/index_ol_ascending.xhtml">Ascending list</a> |
				<a href="/en/weblog/index_ol_descending.xhtml">Descending list</a>
			</p>
			<hr/>
			<p>
				Jump to entry:
				<a href="/en/weblog/2015/03-March/07.xhtml">&lt;&lt;First</a>
				<a rel="prev" href="/en/weblog/2017/01-January/31.xhtml">&lt;Previous</a>
				<a rel="next" href="/en/weblog/2017/02-February/02.xhtml">Next&gt;</a>
				<a href="/en/weblog/latest.xhtml">Latest&gt;&gt;</a>
			</p>
			<hr/>
		</nav>
		<header>
			<h1><abbr title="Extensible Hypertext Markup Language">XHTML</abbr> 5.1</h1>
			<p>Day 00697: Wednesday, 2017 February 01</p>
		</header>
<img src="/img/CC_BY-SA_4.0/y.st./weblog/2017/02/01.jpg" alt="Some plant with both green and purple leaves" class="weblog-header-image" width="800" height="480" />
<section id="general">
	<h2>General news</h2>
	<p>
		Someone mentioned today that the license reference that&apos;s been present in my older edited photographs isn&apos;t present in my newer, unedited photographs.
		I knew that this was the case as soon as I made the transition, but didn&apos;t consider it problematic at the time.
		However, their concerns are valid, so to rectify this, I&apos;ve amended the footer of my website to provide more complete licensing information.
		Every file of this website is released under the <abbr title="GNU&apos;s Not Unix">GNU</abbr> <abbr title="General Public License">GPL</abbr>, but the licensing page linked to in the footer explains the dual-licensing of individual, non-text-based files, including images.
	</p>
	<p>
		After having updated every page of the website (which was minimal effort on my end because of my use of a template, but required a full reupload of the entire website), I found out that the <abbr title="World Wide Web Consortium">W3C</abbr> is working on <abbr title="Extensible Hypertext Markup Language">XHTML</abbr> 5.2.
		That means that <abbr title="Extensible Hypertext Markup Language">XHTML</abbr> 5.1 is already out!
		After verifying that fact, I modified my template again and prepared to reuploaded once more.
		I held off on the actual upload though until I finalized my journal entry for the day.
		In theory, it doesn&apos;t matter whether I say my pages are written in <abbr title="Extensible Hypertext Markup Language">XHTML</abbr>5 or <abbr title="Extensible Hypertext Markup Language">XHTML</abbr> 5.1, but in practice, it sort of does.
		<abbr title="Extensible Hypertext Markup Language">XHTML</abbr>5 is an overlap, where the standards-setting <abbr title="World Wide Web Consortium">W3C</abbr> and the noxious <abbr title="Web Hypertext Application Technology Working Group">WHATWG</abbr> agree on a name.
		However, with <abbr title="Extensible Hypertext Markup Language">XHTML</abbr> 5.1 out, I can show my support for the <abbr title="World Wide Web Consortium">W3C</abbr>&apos;s side, the side of freezing standards and having different document format versions, and my opposition to the <abbr title="Web Hypertext Application Technology Working Group">WHATWG</abbr>&apos;s side, the side of a &quot;living standard&quot; in which old documents are interpreted according to a new standard that they might not even measure up to because the standard is only days old and the document is years old.
		I&apos;m peeved with the <abbr title="Web Hypertext Application Technology Working Group">WHATWG</abbr> so much, they killed <abbr title="Extensible Hypertext Markup Language">XHTML</abbr>2 and resuscitated <abbr title="Hypertext Markup Language">HTML</abbr>.
		I don&apos;t want to look like I support them even a little unless I have to.
	</p>
	<p>
		My <a href="/a/canary.txt">canary</a> still sings the tune of freedom and transparency.
	</p>
</section>
<section id="university">
	<h2>University life</h2>
	<p>
		Before working on my essay, I completed my discussion assignment for the week:
	</p>
	<blockquote>
		<p>
			You say that some club-goers might feel that the music selection is compromised, but how much does the compromised music selection affect these club-goers?
			If these people want to go to a club that plays only unknown bands or some other specific subset of artists, they might have an argument as to why the club should act differently.
			However, that&apos;s not the alternative for It&apos;s My Party.
			The alternative likely involves playing most of the bands that they play now, but with some additions and some subtractions.
			If someone wants a specific play list, they&apos;re on their own to put it together.
			For example, I don&apos;t expect radio stations to ply the music that I listen to, and as far as I know, none do.
			Instead, I buy music and use my own music player.
			When you go to a public venue, such as a club, it&apos;s safe to assume that the entire play list is compromised in every way, and you don&apos;t get any say in the matter (aside from your ability to vote with your money by not going).
		</p>
		<p>
			It&apos;s worth noting too that such compromised play lists are a big reason that I&apos;ve never set foot in a club.
			While I have a problem with compromised play lists, I <strong>*still*</strong> think that anyone that chooses to go to the club must accept the play lists, whatever they are, if the decide to go to a public venue.
			The club-goers have no right to complain about which music is chosen and why.
		</p>
	</blockquote>
	<blockquote>
		<p>
			Is Hurwitz really compromising what they like best?
			What if what Hurwitz likes best has changed since childhood?
			Perhaps now, what they like best now is turning a profit.
		</p>
		<p>
			While I wholly agree that one could look at the ethical issues outside of making money and outside of personal tastes (I do so when I buy my music), I don&apos;t think that these are things that Hurwitz even cares about.
			There&apos;s also the issue of what constitutes a bad message and what doesn&apos;t.
			For example, you mention language and obscenity as a problem, by which I&apos;m gussing that you&apos;re talking about swearing.
			Most of the artists that I listen to don&apos;t seem to swear, but that&apos;s not why I listen to them.
			Many people view swear words as bad, but I view it as people putting too much power in words.
			People are offended by swear words <strong>*because*</strong> said offended parties consider those words as somehow different than other words.
			They&apos;re not different though.
			In my opinion, people need to stop caring about swearing and understand that words are words.
			Contradicting the current culture isn&apos;t necessarily bad either.
			That&apos;s how cultures are changed.
			Change can be either good, bad, or neutral, depending on the change, so contradicting the culture shouldn&apos;t be viewed as bad unless it&apos;s contradicting it in a bad way.
		</p>
	</blockquote>
	<blockquote>
		<p>
			I hadn&apos;t considered the possibility of how things would be different in a non-profit radio station.
			Like you said though, it might not even make a difference there though, as the station may depend on donations to stay on the air waves, so they may still need to cater to their audience.
		</p>
		<p>
			I agree that the questions could be posed as relating to either personal business ethics or institutional business ethics.
			Because there&apos;s no definitive ethical standard, ethics are highly subjective.
			It makes arguing both sides of anything viable, and there&apos;s no way to come to a &quot;correct&quot; answer.
		</p>
	</blockquote>
	<p>
		That cost me much more time than I thought it word, and a lot more than I wanted it too.
		Now, it was time to reread half of my assigned readings and complete my essay for the week.
		I ended up skimming though, and didn&apos;t have time find something useful to the essay on every page as I&apos;d intended.
		Instead, I only four out of ten of the pages.
		Next week should be easier, as I should be less pressed for time.
	</p>
	<p>
		Having finished that, I completed my <a href="https://y.st./en/coursework/PHIL1404/Apple_and_ethics.xhtml">essay</a> as well.
	</p>
	<p>
		It seems that this week&apos;s <span title="Programming Fundamentals">CS 1101</span> activities are to be handled in the <a href="/en/coursework/CS1101/">Learning Journal</a> just like last week&apos;s.
		It&apos;s likely that this is what&apos;s to happen every week in this course, so I won&apos;t mention it again.
	</p>
</section>
		<hr/>
		<p>
			Copyright © 2017 Alex Yst;
			You may modify and/or redistribute this document under the terms of the <a rel="license" href="/license/gpl-3.0-standalone.xhtml"><abbr title="GNU&apos;s Not Unix">GNU</abbr> <abbr title="General Public License version Three or later">GPLv3+</abbr></a>.
			If for some reason you would prefer to modify and/or distribute this document under other free copyleft terms, please ask me via email.
			My address is in the source comments near the top of this document.
			This license also applies to embedded content such as images.
			For more information on that, see <a href="/en/a/licensing.xhtml">licensing</a>.
		</p>
		<p>
			<abbr title="World Wide Web Consortium">W3C</abbr> standards are important.
			This document conforms to the <a href="https://validator.w3.org./nu/?doc=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2017%2F02-February%2F01.xhtml"><abbr title="Extensible Hypertext Markup Language">XHTML</abbr> 5.1</a> specification and uses style sheets that conform to the <a href="http://jigsaw.w3.org./css-validator/validator?uri=https%3A%2F%2Fy.st.%2Fen%2Fweblog%2F2017%2F02-February%2F01.xhtml"><abbr title="Cascading Style Sheets">CSS</abbr>3</a> specification.
		</p>
	</body>
</html>

